Rename default_version from 1.0.0 to stable - #30
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
jnasbyupgrade
force-pushed
the
pin-cat-tools-0.3.0-tag
branch
from
August 6, 2026 21:04
b9a135c to
1efc4de
Compare
The `1.0.0` label was aspirational -- it was never tagged or published to PGXN, despite `default_version` and HISTORY.asc naming it as a real released version. It was carried over from an earlier, incomplete release-prep effort that never actually cut a release. Rename to the `stable` pseudo-version (matching Postgres-Extensions/pg_count_nulls#13's convention) to stop implying a release that never happened, until a real one is actually cut: - extension_drop.control: default_version = 'stable' - sql/extension_drop--1.0.0.sql -> sql/extension_drop--stable.sql (pure rename, no content change) - META.in.json/META.json: roll the version fields back to 0.1.1 (the real last released version), with an X_comment explaining the invariant so it isn't re-bumped prematurely again - HISTORY.asc: rename the "1.0.0" heading to "STABLE" and add an entry explaining the rename Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
META.in.json/META.json: plain version substitution (stable), not a rollback to 0.1.1 with explanatory X_comment lines. HISTORY.asc: just rename the heading, no new changelog entry for an internal versioning-label correction. Also gitignore sql/extension_drop--stable.sql specifically -- it's a mechanical copy of sql/extension_drop.sql for as long as default_version is the stable pseudo-version, so committing it duplicates that file. Real per-version files (once actually released) stay tracked.
jnasbyupgrade
force-pushed
the
rename-1.0.0-to-stable
branch
from
August 6, 2026 21:07
d0c0fe2 to
7c306dd
Compare
jnasbyupgrade
marked this pull request as draft
August 6, 2026 22:05
jnasbyupgrade
marked this pull request as ready for review
August 6, 2026 22:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-opened: the original PR #26 was merged into `fix-cat-tools-install` as
an intermediate branch, but that branch was later force-pushed over during
PR #10's redesign (see #10's history), which overwrote the merge commit.
The content itself was never lost -- it's been carried forward through the
subsequent rebases -- this PR just re-establishes it as a real, reviewable,
mergeable PR instead of living only as a prerequisite branch for #22.
Original description:
extension_drop.control's default_version renamed from the never-actually-
tagged/released "1.0.0" to the "stable" pseudo-version, since nothing has
really shipped yet. Plain s/1.0.0/stable/ substitution in META.in.json/
META.json/HISTORY.asc -- no invented commentary, no rollback to 0.1.1, no
new HISTORY.asc changelog entry for what's purely an internal versioning
correction. Also gitignores sql/extension_drop--stable.sql specifically (a
mechanical copy of sql/extension_drop.sql while on the stable pseudo-
version, not worth committing/duplicating) while keeping real per-version
files tracked once actually released.
Base: stacked on #25 (pin-cat-tools-0.3.0-tag) -- sibling of #19, not
dependent on it. #22 (real-update-path) depends on this landing.